Method and apparatus for discovery of location context identifiers based on approximate location

ABSTRACT

As part of a localized positioning solution, a mobile device may transmit a request message to a server to obtain information about location contexts near the mobile device. In response, the server may, in some implementations, transmit a response message back to the mobile device that identifies a list of nearby LCIs and an area that encompasses these LCIs. The mobile device may store the returned LCI information and the returned area information in corresponding databases for later use. In some implementations, time limits may be placed on the returned area information after which the information is deemed stale.

CLAIM OF PRIORITY UNDER 35 U.S.C. §119

This application is a divisional of and claims priority under 35 USC 120to U.S. patent application Ser. No. 13/295,924, filed Nov. 14, 2011, nowU.S. Pat. No. ______, entitled “METHOD AND APPARATUS FOR DISCOVERY OFLOCATION CONTEXT IDENTIFIERS BASED ON APPROXIMATE LOCATION,” and alsoclaims priority under 35 USC 119 to U.S. Provisional Application Ser.No. 61/414,303, filed Nov. 16, 2010, and entitled, “METHOD FOR DISCOVERYOF INDOOR LCI BASED ON APPROXIMATE LOCATION”, which is assigned to theassignee hereof and which is incorporated herein by reference.

BACKGROUND

1. Field

Subject matter disclosed herein relates generally to positioning and,more specifically, to positioning that may be implemented for alocalized environment.

2. Information

Modern positioning systems typically specify positions that arereferenced to a global coordinate system. However, in some locationbased applications, the use of global coordinates may not be practical.For these applications, positioning solutions that reference a morelocal coordinate system may be desired. In general, it is desirable thatsuch localized positioning solutions operate efficiently.

BRIEF DESCRIPTION OF THE FIGURES

Non-limiting and non-exhaustive implementations will be described withreference to the following figures, wherein like reference numeralsrefer to like parts throughout the various figures unless otherwisespecified.

FIG. 1 is a block diagram illustrating an example mobile devicearchitecture that may be used in an implementation;

FIG. 2 is a block diagram illustrating an example communicationsarrangement in accordance with an implementation;

FIG. 3 is a schematic diagram illustrating an example LCI scenario thatmay exist about a mobile device at a particular point in time inaccordance with an implementation;

FIG. 4 is a flowchart illustrating a method for processing a requestmessage received from a mobile device in accordance with animplementation;

FIG. 5 is a flowchart illustrating a method for obtaining LCIinformation at a mobile device in accordance with an implementation;

FIG. 6 is a flowchart illustrating a method for obtaining LCIinformation at a mobile device in accordance with an implementation; and

FIG. 7 is a flowchart illustrating a method for operating a mobiledevice in accordance with an implementation.

SUMMARY

In one implementation, a machine implemented method for managinglocation context identifier (LCI) requests received from a mobile devicecomprises: receiving a request message for one or more LCIs from amobile device, the request message including location information;determining a region associated with the location information; and ifthere are no known LCIs within the region associated with the locationinformation, transmitting a response message to the mobile device inresponse to the request message that indicates an unavailability of LCIsin the region.

In another implementation, a machine implemented method for obtaininglocation context identifier (LCI) information at a mobile devicecomprises: transmitting a request message for one or more locationcontext identifiers (LCIs) from a mobile device, the request messageincluding location information; and receiving a response message from aserver in response to the request message indicating an unavailabilityof LCIs if there are no known LCIs within a region associated with thelocation information.

In another implementation, a machine implemented method comprises:determining at a mobile device that a location context identifier (LCI)is desired; searching a local database of the mobile device using anestimated location of the mobile device if the estimated location iswithin areas previously returned by one or more directory servers; andtransmitting a request message for one or more LCIs from the mobiledevice if the estimated location is outside areas previously returned bythe one or more directory servers.

In another implementation, an apparatus comprises: means for initiatingtransmission of a request message for one or more location contextidentifiers (LCIs) from a mobile device, the request message includinglocation information; and means for processing a response messagereceived from a server in response to the request message that indicatesan unavailability of LCIs if the server is unable to determine any knownLCIs identifying the region.

In another implementation, an article comprises: a non-transitorystorage medium having machine-readable instructions stored thereon thatare executable by a special purpose computing apparatus to: initiatetransmission of a request message for one or more location contextidentifiers (LCIs) from a mobile device, the request message includinglocation information; and process a response message received from aserver in response to the request message that indicates anunavailability of LCIs, if the server is unable to identify any knownLCIs identifying the region.

In another implementation, a mobile device comprises: a transceiver; anda processor to: initiate transmission of a request message through thetransceiver for one or more location context identifiers (LCIs), therequest message including at least an indication of an estimatedlocation of the mobile device; and process a response message receivedat the transceiver from a server in response to the request message thatindicates an unavailability of LCIs to identify at least one area atleast in part overlapping a region including the estimated location, ifthe server is unable to identify any known LCIs identifying the region.

In another implementation, an apparatus comprises: means for determiningat a mobile device that a location context identifier (LCI) is desired;means for searching a local database of the mobile device for LCIinformation using an estimated location of the mobile device if theestimated location is within areas previously returned by one or moredirectory servers; and means for initiating transmission of a requestmessage for one or more LCIs from the mobile device if the estimatedlocation is outside areas previously returned by the one or moredirectory servers, the request message including at least an indicationof the estimated location of the mobile device.

In another implementation, an article comprises: a non-transitorystorage medium having machine-readable instructions stored thereon whichare executable by a special purpose computing apparatus to: determine ata mobile device that a location context identifier (LCI) is desired;search a local database of the mobile device for LCI information usingan estimated location of the mobile device if the estimated location iswithin areas previously returned by one or more directory servers; andinitiate transmission of a request message for one or more LCIs from themobile device if the estimated location is outside areas previouslyreturned by the one or more directory servers, the request messageincluding at least an indication of the estimated location of the mobiledevice.

In yet another implementation, a mobile device comprises: a transmitter;and a processor to: determine that a location context identifier (LCI)is desired; search a local database of the mobile device for LCIinformation using an estimated location of the mobile device if theestimated location is within areas previously returned by one or moredirectory servers; and initiate transmission of a request messagethrough the transmitter for one or more LCIs from the mobile device ifthe estimated location is outside areas previously returned by the oneor more directory servers, the request message including at least anindication of the estimated location of the mobile device. It should beunderstood that the above identified embodiments and implementations aremerely example embodiments and implementations, and that claimed subjectmatter is not limited in these respects.

DETAILED DESCRIPTION

Reference throughout this specification to “one implementation,” “animplementation,” “certain implementations,” “some implementations,” or“various implementations” means that a particular feature, structure, orcharacteristic described in connection with a described implementationmay be included in at least one implementation of claimed subjectmatter. Thus, appearances of the phrase “in one example implementation,”“in an example implementation,” “in certain example implementations,”“in some example implementations,” or “in various exampleimplementations” in various places throughout this specification are notnecessarily all referring to the same implementation(s). Furthermore,particular features, structures, or characteristics may be combined inone or more implementations.

Mobile devices often have the ability to estimate location and/orposition with a high degree of precision using any one of severaltechnologies. These technologies may include, for example, satellitepositioning systems (e.g., the Global Positioning System (GPS), etc.),advanced forward link trilateration (AFLT), multilateration, and/orothers. Using high precision location information, applications for amobile device may provide a user with different services such as, forexample, vehicle/pedestrian navigation, location-based searching, and/orother services. Here, high precision location information may beprocessed according to a global coordinate system (e.g., latitude andlongitude, earth centered xyz coordinates, etc). While the use oflocation information referenced to a global coordinate system may beuseful in providing some services (e.g., outdoor vehicle navigation,etc.), such location information may be impractical for other types ofservices such as, for example, indoor pedestrian navigation. For theseservices, positioning solutions that reference a more local coordinatesystem may be used.

As used herein, the term “localized environment” may include anylocalized space where positioning services referenced to a localcoordinate system may be desired including, for example, indoor areas,such as a building, and also outdoor areas or hybrid indoor/outdoorareas, such as an apartment complex, a golf course, or an airport. Insome localized positioning solutions, a localized environment mayinclude a number of locally defined areas, or location contexts, withinwhich positioning takes place. These location contexts may be identifiedusing location context identifiers (LCIs) during positioning relatedoperations. In one example scenario, a building may represent alocalized environment and each floor of the building may represent adifferent location context having a corresponding LCI. In some otherscenarios, large floors of a building may be divided into multiplelocation contexts (e.g., terminals of an airport, etc.). Many otherarrangements for defining location contexts may alternatively be usedand may, for example, depend upon the specific geometry and/orcomplexity of the corresponding environment. A localized positioningsolution may also include one or more directory servers that may beaccessed by mobile devices to obtain information about a localizedenvironment. LCIs may uniquely identify location contexts such as areaswithin a region.

In various implementations, a mobile device may desire LCI informationfor any of a number of different purposes. For example, LCIs may be usedas handles for requesting additional information about location contextsfrom one or more servers. This additional information may include, forexample, map information for a location context or information to beoverlaid on a map (e.g., routes, paths, points of interest, locations ofbeacons or access points, heat map data, etc.). LCIs may also be used,for example, to obtain information for use in performing location-basedapplications, such as pedestrian navigation. Other uses of LCIinformation by mobile devices also exist.

FIG. 1 is a block diagram illustrating an example mobile devicearchitecture 200 that may be used in an implementation. As illustrated,the mobile device architecture 200 may include, for example, a generalpurpose processor 202, a digital signal processor 204, a wirelesstransceiver 206, a radio receiver 208, a memory 210, and an SPS receiver212. A bus 222 or other alternative structure or structures may beprovided for establishing interconnections between various components ofthe architecture 200. In the illustrated implementation, one or moreinterfaces 214, 216, 218, 220 may be provided between selectedcomponents and bus 222. The wireless transceiver 206, the radio receiver208, and the SPS receiver 212 may each be coupled to one or moreantennas 224, 226, 228, and/or other transducers, to facilitate thetransmission and/or reception of wireless signals.

The general purpose processor 202 and the digital signal processor 204are digital processing devices that are capable of executing programs toprovide one or more functions and/or services to a user. One or both ofthese processors 202, 204 may be used, for example, to execute anoperating system of a corresponding wireless device. One or both ofthese processors 202, 204 may also be used, for example, to execute userapplication programs including, for example, location-based applicationsthat may rely on the availability of an accurate position estimate. Inaddition, one or both of these processors 202, 204 may be used toimplement, either partially or fully, one or more of the positioningrelated processes or techniques described herein in someimplementations. It should be appreciated that other forms of digitalprocessing devices may additionally or alternatively be used to performsome or all of the described functions in various implementationsincluding, for example, one or more controllers, microcontrollers,application specific integrated circuits (ASICs), field programmablegate arrays (FPGAs), programmable logic arrays (PLAs), programmablelogic devices (PLDs), reduced instruction set computers (RISCs), and/orothers, including combinations of the above.

Wireless transceiver 206 may include any type of transceiver that iscapable of supporting wireless communication with one or more remotewireless entities. In various implementations, wireless transceiver 206may be configured in accordance with one or more wireless networkingstandards and/or wireless cellular standards. In some implementations,multiple wireless transceivers may be provided to support operation withdifferent networks or systems in a surrounding environment. Duringmobile device operation, wireless transceiver 206 may be called upon tocommunicate with a base station or access point of a wirelesscommunication system or network. Radio receiver 208 may be operative forreceiving signals from one or more sensors of a sensor network or othertransmitting nodes within a surrounding environment.

Memory 210 may include any type of device or component, or combinationof devices and/or components, that is capable of storing digitalinformation (e.g., digital data, computer executable instructions and/orprograms, etc.) for access by a processing device or other component.This may include, for example, semiconductor memories, magnetic datastorage devices, disc based storage devices, optical storage devices,read only memories (ROMs), random access memories (RAMs), non-volatilememories, flash memories, USB drives, compact disc read only memories(CD-ROMs), DVDs, Blu-Ray disks, magneto-optical disks, erasableprogrammable ROMs (EPROMs), electrically erasable programmable ROMs(EEPROMs), magnetic or optical cards, and/or other digital storagesuitable for storing electronic instructions and/or data.

SPS receiver 212 may include any type of receiver capable of receivingSPS signals from positioning satellites and processing the signals toprovide one or more position estimates for a mobile device. SPS receiver212 may be configured to operate with any existing or future SPS systemincluding, for example, the Global Positioning System (GPS), the GLONASSsystem, the Compass system, the Galileo system, the IRNSS system, theGNSS system and other systems that use Satellite Based AugmentationSystems (SBASs) and/or Ground Based Augmentations Systems (GBASs),and/or other satellite navigation systems. In some implementations, oneor more of the processes or techniques described herein may beimplemented, either partially or fully, within SPS receiver 212 or asimilar structure. It should be appreciated that the mobile devicearchitecture 200 of FIG. 1 represents one possible example of anarchitecture that may be used in a implementation. Other architecturesmay alternatively be used. It should also be appreciated that all orpart of the various devices, processes, or methods described herein maybe implemented using any combination of hardware, firmware, and/orsoftware.

FIG. 2 is a block diagram illustrating an example communicationsarrangement 10 in accordance with an implementation. As illustrated, amobile device 12 may wirelessly communicate with a server 14 (e.g., adirectory server, etc.) to obtain information about a localizedenvironment that mobile device 12 is operating within or is approaching.As will be discussed in greater detail, this information may include,among other things, LCIs identifying location contexts of the localizedenvironment that are proximate to mobile device 12. Mobile device 12 maythen use these LCIs to perform, for example, positioning functions orposition related applications (e.g., pedestrian navigation, etc.).Mobile device 12 may utilize mobile device architecture 200 of FIG. 1 ora similar architecture in some implementations. In the illustratedimplementation, server 14 may include: a memory 16, a processor 18, awireless transceiver 20, and a bus 22. These elements may be similar instructure and/or function to the corresponding elements of FIG. 1described above. Memory 16 may include any type of device or component,or combination of devices and/or components, that is capable of storingdigital information (e.g., digital data, computer executableinstructions and/or programs, etc.) for access by a processing device orother component. This may include, for example, semiconductor memories,magnetic data storage devices, disc based storage devices, opticalstorage devices, read only memories (ROMs), random access memories(RAMs), non-volatile memories, flash memories, USB drives, compact discread only memories (CD-ROMs), DVDs, Blu-Ray disks, magneto-opticaldisks, erasable programmable ROMs (EPROMs), electrically erasableprogrammable ROMs (EEPROMs), magnetic or optical cards, and/or otherdigital storage suitable for storing electronic instructions and/ordata. Other server architectures may alternatively be used. In someimplementations, wireless transceiver 20 may be located outside ofserver 14. For example, in one possible approach, server 14 maycommunicate with wireless transceiver 20 via a wired network (e.g., anintranet, the Internet, etc.). Server 14 may include, for example, anetwork interface card (NIC) or similar functionality to facilitatecommunication over the wired network.

In a localized positioning solution, the number of directory servers maybe limited and these servers may need to be shared by a large number ofmobile devices. If the number of devices attempting to access adirectory server at a particular time is large, processing delays mayoccur that may compromise the performance of, for example,position-based user applications. Techniques, processes, and structuresare provided herein that may reduce the frequency of server accesses bymobile devices in a localized positioning solution. In some instances,these reductions in communication activity between mobile devices anddirectory servers may result in power savings within a mobile device by,for example, reducing transceiver activity. Various described approachesmay also, in some implementations, decrease a time-to-fix (TTF) at amobile device.

In at least one implementation, mobile device 12 may, after determiningthat an LCI is desired, transmit a request message to server 14 toidentify one or more LCIs identifying areas in a vicinity of mobiledevice 12. As part of the request message, mobile device 12 may includean indication of its estimated location or some other locationinformation. Any format for indicating an estimated location may beused. In one possible approach, a position and an uncertainty value maybe used to indicate an estimated location. The position may identify acentral point and the uncertainty may identify an area about the centralpoint (e.g., a radius defining a circular area, information defining anellipse or some other shape, etc.) where it is believed mobile device 12is likely to be. In response to the request message, server 14 maysearch a database of LCIs to find one or more LCIs identifying areasthat are close to the estimated location of mobile device 12.

FIG. 3 is a schematic diagram illustrating an example LCI scenario 28that may exist about mobile device 12 at a particular point in time inaccordance with an implementation. As shown, mobile device 12 may havean estimated location 30 having position x with uncertainty y. As usedherein, a position x with uncertainty y may be referred to as a “key.” Anumber of different techniques may be used by mobile device 12 toestimate its current location. For example, in one implementation,mobile device 12 may use a last-known satellite positioning system (SPS)fix as a current estimated location (e.g., a last-known GlobalPositioning System (GPS) fix, etc.). In another implementation, mobiledevice 12 may scan wireless network access points or base stations(e.g., IEEE 802.11 access points, cellular base stations, etc.) in asurrounding area to develop an estimated location. Mobile device 12 may,for example, use a location of a cell or coverage area of a currentlyassociated access point or base station as an estimated location in someimplementations. In some other implementations, mobile device 12 may useinput from a user to determine a location estimate. In still otherimplementations, an on-board camera of mobile device 12 may be used tocapture images of a surrounding environment from which a locationestimate may be implied. Many other techniques, including combinationsof techniques, may be used to determine a location estimate for mobiledevice 12.

Upon receiving a request message, server 14 may use estimated location30 (or other location information) to search for LCIs identifying areasnear mobile device 12. With reference to FIG. 3, server 14 may find, forexample, first LCI 40, second LCI 42, third LCI 44, and fourth LCI 46during a database search. Server 14 may then transmit a response messageto mobile device 12 that includes a list of these LCIs. In someimplementations, the list of LCIs may also include location contextsidentified by the listed LCIs, thus allowing mobile device 12 todetermine which identified area is closest. In addition to the list ofLCIs, the response message may include an indication of an area 48 thatencompasses location contexts identified by the LCIs on the list as wellas the estimated location 30 of mobile device 12. In one possibleapproach, as illustrated in FIG. 3, area 48 may be described as aposition x′ and an uncertainty y′ that defines a circle (where x′ formsthe center and y′ defines a radius). As used herein, a position x′ anduncertainty y′ may be referred to as an “alternate key.” In otherimplementations, other shapes and/or other formats for describing suchan area may be used. In at least one implementation, all of the LCIsidentifying areas that are encompassed by area 48 are included on thelist of LCIs in the response message.

After mobile device 12 receives the response message, it may cache theLCI information of the message within a local database. The localdatabase may be stored within, for example, memory 210 of FIG. 1 or someother digital data storage structure. In some implementations, mobiledevice 12 may use the LCI information from the response message toobtain additional information about the listed LCIs. For example, mobiledevice 12 may contact map servers to request information on, forexample, access points (APs), base stations (BSs), or other wirelessnetwork nodes associated with location contexts identified by listedLCIs. This additional information may also be cached in the localdatabase. Mobile device 12 may also cache information about area 48within a “previously returned areas” database. The previously returnedareas database may track areas for which LCI information was previouslyprovided to mobile device 12 from server 14 and/or other servers. Thepreviously returned areas database may be stored within, for example,memory 210 of FIG. 1 or some other digital data storage structure.

In certain implementations, if mobile device 12 determines that an LCIis desired, it may first check its previously returned areas databaseusing an estimated location of mobile device 12 before any requestmessages are transmitted to a server. If the previously returned areasdatabase indicates that the estimated location is within a previouslyreturned area, the mobile device 12 may search its local database forLCIs using the estimated location as, for example, a key. Because theestimated location is within a previously returned area, the mobiledevice 12 does not need to contact server 14 to request an LCI. Thistends to reduce communication traffic levels experienced by server 14.

In some instances, after receiving an LCI request message, server 14 mayfind that there are no known LCIs covering an area in a vicinity ofmobile device 12. In such a case, server 14 may return a responsemessage that includes an empty list of LCIs. In addition, in someimplementations, server 14 may return an indication of an area withinwhich the mobile device is not to transmit a subsequent request message.In certain implementations, the area may be specified as a position x′and an uncertainty y′. In one possible approach, the uncertainty y′ ofthe returned area information may be made as large as possible withoutencompassing areas identified by any known LCIs. For example, in onepossible scenario, if server 14 finds that there are no LCIs identifyingareas in a current city of a location of the mobile device, then theuncertainty of the returned area information may be made large enough toencompass the entire city. In other implementations, limits may beplaced on the maximum size of the returned uncertainty information. Theposition x′ of the returned area information may, in someimplementations, be made the same as the position x of the estimatedlocation of mobile device 12 if no LCIs identifying nearby areas arefound. Other formats for describing returned area information in aresponse message when no LCIs identifying nearby areas are found mayalternatively be used.

If mobile device 12 receives a response message having an empty LCIlist, it may cache the returned area information into the previouslyreturned areas database. This response message information may beutilized to prevent mobile device 12 from sending extraneous LCIrequests to directory servers in the future if an estimated location ofmobile device 12 is within the returned area. If the uncertainty of thereturned area information is made large enough to encompass an entirecity, the mobile device 12 may not send any LCI request messages whileit is inside the city limits as such LCI request messages would mostlikely be unfruitful.

Over time, new LCIs may be added to identify areas in a localizedenvironment. In some implementations, mechanisms are provided that mayallow a mobile device to become aware of a new LCI even if it identifiesan area that is located within an area listed in the previously returnedareas database. This may be done by, for example, applying a time limitto information within the previously returned areas database thatprevents the information stored therein from becoming stale. In onepossible approach, server 14 may associate a time-to-live (TTL) value toan area indication it returns to mobile device 12 in a response message.After receiving the response message, mobile device 12 may record thetime that the response message was received and cache the areainformation in the previously returned areas database. Mobile device 12may then track the age of the area information within the previouslyreturned areas database. As the age of the area information reaches theTTL value, the information may be tagged as stale, after which it is nolonger used. In certain implementations, the returned area informationmay be deleted from the previously returned areas database as a resultof becoming stale. In an alternative approach, mobile device 12 mayapply its own TTL value to area information in a newly received responsemessage. Alternative techniques for time limiting area informationwithin a previously returned areas database may be used in otherimplementations.

FIG. 4 is a flowchart illustrating a method 50 for processing a requestmessage received from a mobile device in accordance with animplementation. The method 50 may be implemented by, for example, aserver or other structure associated with a localized positioningsolution (e.g., server 14 of FIG. 2, etc.). A request message for one ormore LCIs is first received from a mobile device, the request messageincluding location information (block 52). The location information mayinclude information collected and/or generated by the mobile device thatis related in some manner to the location of the mobile device. In thismanner, the location information may include, for example, an estimatedlocation of the mobile device, locations of wireless transceivers (e.g.,base stations, access points, etc.) visible to the mobile device,identities of visible transceivers, identities of satellites visible tothe mobile device, a service set identifier (SSID), a basic service setidentifier (BSSID), a base station identifier (BSID), sensor readingssuch as dead reckoning information, and/or other location information.In at least one implementation, the location information may include,for example, a position x and an uncertainty y or some other format fordescribing an estimated location of the mobile device. After the requestmessage is received, a region associated with the location informationmay be determined (block 54). The region associated with the locationinformation may include a region within which known LCIs will besearched for the mobile device. For example, if the location informationincludes an estimated location of the mobile device, the region mayinclude a region that encompasses the estimated location. In someimplementations, the region may be defined as a region including allpoints within a certain distance of a center of the estimated location.Other techniques for determining the region may alternatively be used.If the request message includes other types of location information(e.g., locations and identities of visible transceivers, etc.), thedetermination of a region may involve, for example, first generating anestimate of the location of the mobile device.

A database may be searched for known LCIs in the region associated withthe location information (block 56). If one or more known LCIs are found(block 58-Y), a response message may be transmitted to the mobile devicethat lists the one or more known LCIs and also indicates an area thatencompasses the one or more known LCIs (block 58). In at least oneimplementation, this area may be an area that encompasses the one ormore known LCIs and also an estimated location of the mobile device. Insome implementations, the returned area may be specified as a positionx′ and an uncertainty y′. Other formats for describing the returned areamay alternatively be used. In some implementations, a TTL indication maybe included in the response message that indicates a time period afterwhich LCI information (e.g., the list of LCIs, the area information,and/or other LCI information) in the message is deemed stale. Asdescribed previously, in at least one implementation, all known LCIsidentifying areas that are encompassed by the returned area are includedin the list of LCIs in the response message. The term “known” may beused here to indicate LCIs that are known by the server or otherstructure implementing the method 50 (e.g., LCIs recorded within adatabase of server 14 of FIG. 2, etc.). As will be described in greaterdetail, upon receipt of a response message, a mobile device may storearea information from the message in a returned areas database in someimplementations.

If there are no known LCIs in the region (block 58-N), a responsemessage may be transmitted to the mobile device that indicates anunavailability of LCIs (block 60). In one possible approach, theresponse message may include, for example, an empty list of LCIs. Othertechniques for indicating an unavailability of LCIs may alternatively beused. In some implementations, the response message may also indicate anarea that encompasses the region associated with the locationinformation and that also includes no known LCIs. This area may belarger than the region associated with the location information. Thearea may be selected based, at least in part, on information within, forexample, an LCI database accessible by a server. In certainimplementations, the area may be specified in the response message as aposition x′ and an uncertainty y′. In one possible approach, forexample, the uncertainty y′ of the returned area information may be madeas large as possible without encompassing any areas identified by knownLCIs (although size limits may be used in some implementations). Otherformats for describing area information in a response message if no LCIsare found may alternatively be used. As will be described in greaterdetail, upon receipt of a response message, a mobile device may storearea information from the message in a returned areas database in someimplementations. The response message may also include a TTL indicationindicating a time period after which the area indication is consideredstale.

FIG. 5 is a flowchart illustrating a method 70 for obtaining LCIinformation at a mobile device in accordance with an implementation. Arequest message for one or more location context identifiers (LCIs) isfirst transmitted from a mobile device, where the request messageincludes location information (block 72). The content of the locationinformation has been described above. A response message may then bereceived from a server in response to the request message that indicatesan unavailability of LCIs, if the server could find no known LCIs withina region associated with the location information (block 74). The regionassociated with the location information has been described above. Inaddition to the LCI unavailability indication, the response message mayalso include area information as described previously. In someimplementations, the area information may be stored by the mobile devicein a previously returned areas database associated with the mobiledevice (block 76). After receiving the response message, the mobiledevice may refrain from transmitting a subsequent request message untilthe device leaves the indicated area (block 78). In some implementation,some or all of the area information stored within the previouslyreturned areas database may be time limited (e.g., the information maybe considered stale after a specific time period has elapsed).

FIG. 6 is a flowchart illustrating a method 80 for obtaining LCIinformation at a mobile device in accordance with an implementation. Arequest message for one or more LCIs may first be transmitted from amobile device, where the request message includes location information(block 82). A response message may then be received at the mobile devicein response to the transmitted request message indicating one or moreknown LCIs within a region associated with the location information andan area that encompasses the one or more known LCIs, if one or moreknown LCIs are found within the region by a server (block 84). Inresponse to receipt of the response message, the mobile device may storearea information in a previously returned areas database and LCIinformation in a local database (block 86). In some implementations, aTTL indication may be included in a response message to indicate a timeperiod after which the returned area information and/or the LCIindications in the message is deemed stale. The mobile device may recordthis TTL information and delete or tag as stale the corresponding storedinformation at an appropriate time. In various implementations, the areaindicated in the response message that encompasses the one or more knownLCIs may also encompass an estimated location of the mobile device.

FIG. 7 is a flowchart illustrating a method 100 for operating a mobiledevice in accordance with an implementation. If a mobile devicedetermines that an LCI is desired, an LCI lookup procedure may beinitiated (block 102). It is first determined whether an estimatedlocation of the mobile device is within areas specified within apreviously returned areas database (block 104). If the estimatedlocation is within the previously returned areas database (block 104-Y),then the mobile device may search a local database for LCI informationusing the estimated location (block 106). A list of candidate LCIs maythen be returned and a directory server does not need to be contacted(block 108). If the estimated location is not within the previouslyreturned areas database (block 104-N), then the mobile device maytransmit an LCI request message that includes an indication of theestimated location to a directory server (block 110). A response messagemay then be received from the server that includes a list of candidateLCIs and an indication of a corresponding area that encompasses areasidentified by the LCIs in the list (block 112). The mobile device maythen store the LCI information from the list in a local database and thearea information in the previously returned areas database (block 114).The mobile device may also transmit information request messages toother servers at this time to obtain additional information about theLCIs on the list. This additional information may also be stored withinthe previously returned areas database. The mobile device may thensearch the local database using the estimated location (block 106) andreturn a list of candidate LCIs (block 108).

The terms, “and”, “or”, and “and/or” as used herein may include avariety of meanings that also are expected to depend at least in partupon the context in which such terms are used. Typically, “or” if usedto associate a list, such as A, B or C, is intended to mean A, B, and C,here used in the inclusive sense, as well as A, B or C, here used in theexclusive sense. In addition, the term “one or more” as used herein maybe used to describe any feature, structure, or characteristic in thesingular or may be used to describe a plurality or some othercombination of features, structures or characteristics. Though, itshould be noted that this is merely an illustrative example and claimedsubject matter is not limited to this example.

The methodologies described herein can be implemented by various meansdepending upon the application. For example, these methodologies can beimplemented in hardware, firmware, software, or a combination thereof.For hardware implementations, processing may be implemented within, forexample, one or more application specific integrated circuits (ASICs),digital signal processors (DSPs), digital signal processing devices(DSPDs), programmable logic devices (PLDs), field programmable gatearrays (FPGAs), processors, controllers, micro-controllers,microprocessors, electronic devices, other electronic units designed toperform the functions described herein, or a combination thereof.Herein, the term “control logic” encompasses logic implemented bysoftware, hardware, firmware, or a combination.

For a firmware and/or software implementation, methodologies can beimplemented with modules (e.g., procedures, functions, and so on) thatperform functions described herein. Any machine readable digital mediumtangibly embodying instructions can be used in implementingmethodologies described herein. For example, software codes can bestored in a storage medium and executed by a processing unit. Storagecan be implemented within a processing unit or external to a processingunit. As used herein, the terms “storage medium,” “storage media,”“storage device,” “digital storage,” or the like refer to any type oflong term, short term, volatile, nonvolatile, or other storagestructures and are not to be limited to any particular type of memory ornumber of memories, or type of media upon which data is stored.

If implemented in firmware and/or software, the functions may be storedas one or more instructions or code on a computer readable medium.Examples include computer readable media encoded with a data structureand computer readable media encoded with a computer program.Computer-readable media may take the form of an article of manufacture.Computer-readable media includes physical computer storage media. Acomputer readable storage medium may be any available digital mediumthat can be accessed by a computer. By way of example, and notlimitation, such computer-readable media can comprise RAM, ROM, EEPROM,CD-ROM or other optical disk storage, magnetic disk storage or othermagnetic storage devices, or any other medium that can be used to storedesired program code in the form of instructions or data structures andthat can be accessed by a computer; disk and disc, as used herein,includes compact disc (CD), laser disc, optical disc, digital versatiledisc (DVD), floppy disk and Blu-ray disc where disks usually reproducedata magnetically, while discs reproduce data optically with lasers.Combinations of the above should also be included within the scope ofcomputer-readable media.

Techniques described herein may be implemented in conjunction withvarious wireless communication networks such as, for example, a wirelesswide area network (WWAN), a wireless local area network (WLAN), awireless personal area network (WPAN), and so on. The terms “network”and “system” may be used interchangeably. The terms “position” and“location” may be used interchangeably. A WWAN may be a Code DivisionMultiple Access (CDMA) network, a Time Division Multiple Access (TDMA)network, a Frequency Division Multiple Access (FDMA) network, anOrthogonal Frequency Division Multiple Access (OFDMA) network, aSingle-Carrier Frequency Division Multiple Access (SC-FDMA) network, aLong Term Evolution (LTE) network, a WiMAX (IEEE 802.16) network, and soon. A CDMA network may implement one or more radio access technologies(RATs) such as, for example, cdma2000, Wideband-CDMA (W-CDMA), and soon. Cdma2000 may include IS-95, IS-2000, and IS-856 standards. A TDMAnetwork may implement Global System for Mobile Communications (GSM),Digital Advanced Mobile Phone System (D-AMPS), or some other RAT. GSMand W-CDMA are described in documents from a consortium named “3rdGeneration Partnership Project” (3GPP). Cdma 2000 is described indocuments from a consortium named “3rd Generation Partnership Project 2”(3GPP2). 3GPP and 3GPP2 documents are publicly available. A WLAN may be,for example, an IEEE 802.11x network or some other type of network. AWPAN may be, for example, a Bluetooth network, an IEEE 802.15x network,or some other type of network. Techniques disclosed herein may also beimplemented in conjunction with any combination of WWAN, WLAN, and/orWPAN.

As used herein, the term “mobile device” refers to a device such as acellular telephone, smart phone, or other wireless communication device;a personal communication system (PCS) device; a personal navigationdevice (PND); a Personal Information Manager (PIM); a Personal DigitalAssistant (PDA); a laptop computer; a tablet computer; a portable mediaplayer; or other suitable mobile or portable device which is capable ofreceiving wireless communication and/or navigation signals. The term“mobile device” is also intended to include devices which communicatewith a personal navigation device (PND), such as by short-rangewireless, infra-red, wireline connection, or other connection,regardless of whether satellite signal reception, assistance datareception, and/or position-related processing occurs at the device or atthe PND. Also, the term “mobile device” is intended to include alldevices, including wireless communication devices, computers, laptops,etc. which are capable of communication with a server, such as via theInternet, Wi-Fi, or other network, and regardless of whether satellitesignal reception, assistance data reception, and/or position-relatedprocessing occurs at the device, at a server, or at another deviceassociated with the network. Any operable combination of the above arealso considered a “mobile device.”

Designation that something is “optimized,” “required,” or other similardesignation does not indicate that the current disclosure applies onlyto systems that are optimized, or systems in which the “required”elements are present (or other limitation due to other designations).These designations refer only to the particular describedimplementation. Of course, many implementations are possible. Thetechniques can be used with protocols other than those discussed herein,including protocols that are in development or to be developed.

In the preceding detailed description, numerous specific details havebeen set forth to provide a thorough understanding of claimed subjectmatter. However, it will be understood by those skilled in the art thatclaimed subject matter may be practiced without these specific details.In other instances, methods or structures that would be known by one ofordinary skill have not been described in detail so as not to obscureclaimed subject matter.

Some portions of the preceding detailed description have been presentedin terms of logic, algorithms, or symbolic representations of operationson binary states stored within a storage medium of a specific apparatusor special purpose computing device or platform. In the context of thisparticular specification, the term specific apparatus or the like mayinclude a general purpose computer once it is programmed to performparticular functions pursuant to instructions from program software.Algorithmic descriptions or symbolic representations are examples oftechniques used by those of ordinary skill in the signal processing orrelated arts to convey the substance of their work to others skilled inthe art. An algorithm is here, and generally, considered to be aself-consistent sequence of operations or similar signal processingleading to a desired result. In this context, operations or processinginvolve physical manipulation of physical quantities. Typically,although not necessarily, such quantities may take the form ofelectrical or magnetic signals capable of being stored, transferred,combined, compared or otherwise manipulated as electronic signalsrepresenting information. It has proven convenient at times, principallyfor reasons of common usage, to refer to such signals as bits, data,values, elements, symbols, characters, terms, numbers, numerals,information, or the like. It should be understood, however, that all ofthese or similar terms are to be associated with appropriate physicalquantities and are merely convenient labels.

Unless specifically stated otherwise, as apparent from the followingdiscussion, it is appreciated that throughout this specificationdiscussions utilizing terms such as “processing,” “computing,”“calculating,” “determining,” “establishing,” “obtaining,”“identifying,” “selecting,” “generating,” “estimating,” “initializing,”or the like may refer to actions or processes of a specific apparatus,such as a special purpose computer or a similar special purposeelectronic computing device. In the context of this specification,therefore, a special purpose computer or a similar special purposeelectronic computing device is capable of manipulating or transformingsignals, typically represented as physical electronic or magneticquantities within memories, registers, or other information storagedevices, transmission devices, or display devices of the special purposecomputer or similar special purpose electronic computing device. In thecontext of this particular patent application, the term “specificapparatus” may include a general purpose computer once it is programmedto perform particular functions pursuant to instructions from programsoftware.

A computer-readable storage medium typically may be non-transitory orcomprise a non-transitory device. In this context, a non-transitorystorage medium may include a device that is tangible, meaning that thedevice has a concrete physical form, although the device may change itsphysical state. Thus, for example, non-transitory refers to a deviceremaining tangible despite this change in state.

A satellite positioning system (SPS) typically includes a system oftransmitters positioned to enable entities to determine their locationon or above the Earth based, at least in part, on signals received fromthe transmitters. Such a transmitter typically transmits a signal markedwith a repeating pseudo-random noise (PN) code of a set number of chipsand may be located on ground based control stations, user equipmentand/or space vehicles. In a particular example, such transmitters may belocated on Earth orbiting satellite vehicles (SVs). For example, a SV ina constellation of Global Navigation Satellite System (GNSS) such asGlobal Positioning System (GPS), Galileo, Glonass or Compass maytransmit a signal marked with a PN code that is distinguishable from PNcodes transmitted by other SVs in the constellation (e.g., usingdifferent PN codes for each satellite as in GPS or using the same codeon different frequencies as in Glonass). In accordance with certainaspects, the techniques presented herein are not restricted to globalsystems (e.g., GNSS) for SPS. For example, the techniques providedherein may be applied to or otherwise enabled for use in variousregional systems, such as, e.g., Quasi-Zenith Satellite System (QZSS)over Japan, Indian Regional Navigational Satellite System (IRNSS) overIndia, Beidou over China, etc., and/or various augmentation systems(e.g., an Satellite Based Augmentation System (SBAS)) that may beassociated with or otherwise enabled for use with one or more globaland/or regional navigation satellite systems. By way of example but notlimitation, an SBAS may include an augmentation system(s) that providesintegrity information, differential corrections, etc., such as, e.g.,Wide Area Augmentation System (WAAS), European Geostationary NavigationOverlay Service (EGNOS), Multi-functional Satellite Augmentation System(MSAS), GPS Aided Geo Augmented Navigation or GPS and Geo AugmentedNavigation system (GAGAN), and/or the like. Thus, as used herein an SPSmay include any combination of one or more global and/or regionalnavigation satellite systems and/or augmentation systems, and SPSsignals may include SPS, SPS-like, and/or other signals associated withsuch one or more SPS.

While there has been illustrated and described what are presentlyconsidered to be example features, it will be understood by thoseskilled in the art that various other modifications may be made, andequivalents may be substituted, without departing from claimed subjectmatter. Additionally, many modifications may be made to adapt aparticular situation to the teachings of claimed subject matter withoutdeparting from the central concept described herein.

Therefore, it is intended that claimed subject matter not be limited toparticular disclosed examples, but that such claimed subject matter mayalso include all aspects falling within the scope of appended claims,and equivalents thereof

What is claimed is:
 1. A machine implemented method for managinglocation context identifier (LCI) requests received from a mobiledevice, comprising: receiving a request message for one or more LCIsfrom said mobile device, said request message comprising locationinformation; determining a region associated with said locationinformation; and transmitting a response message to said mobile devicein response to said request message that indicates an unavailability ofLCIs in said region at least partially in response to determining thatthere are no known LCIs within said region associated with said locationinformation.
 2. The method of claim 1, wherein said response messagecomprises an empty list of LCIs.
 3. The method of claim 1, furthercomprising: determining an area that encompasses said region associatedwith said location information and that includes no known LCIs at leastpartially in response to determining that there are no known LCIs withinsaid region associated with said location information, wherein saidresponse message comprises an indication of said area.
 4. The method ofclaim 3, wherein: determining said area that encompasses said regionassociated with said location information comprises identifying an areathat is larger than said region associated with said locationinformation at least partially in response to determining that there areno known LCIs just outside a boundary of said region.
 5. The method ofclaim 3, further comprising: determining said area that encompasses saidregion associated with said location information comprises identifyingan area that is as large as possible, up to a limit, withoutencompassing any known LCIs.
 6. The method of claim 3, wherein: saidresponse message comprises a time-to-live indication identifying a timeafter which said indication of said area is considered stale.
 7. Themethod of claim 1, wherein: said location information comprises anestimate of a location of said mobile device.
 8. The method of claim 7,wherein: said estimate of said location of said mobile device comprisesa position indication and an uncertainty value.
 9. The method of claim1, further comprising: at least partially in response to determiningthat there are one or more known LCIs within said region associated withsaid location information, transmitting a response message to saidmobile device in response to said request message that comprises a listof said one or more known LCIs.
 10. The method of claim 9, wherein: saidresponse message that comprises said list of said one or more known LCIsalso comprises an indication of an area that encompasses said one ormore known LCIs.
 11. A machine implemented method comprising:determining at a mobile device that a location context identifier (LCI)is desired; searching a local database of said mobile device using anestimated location of said mobile device at least partially in responseto determining that said estimated location is within areas previouslyreturned by one or more directory servers; and transmitting a requestmessage for one or more LCIs from said mobile device at least partiallyin response to said estimated location being outside areas previouslyreturned by said one or more directory servers.
 12. The method of claim11, further comprising: after transmitting said request message,receiving a response message from a first directory server responsive tosaid request message, said response message comprising a list of LCIsidentifying areas in a vicinity of said estimated location.
 13. Themethod of claim 12, wherein: said response message further comprises anindication of an area that encompasses said estimated location and saidLCIs in said list of LCIs if said list of LCIs has at least one LCI. 14.The method of claim 13, further comprising: after receiving saidresponse message, storing said area in a previously returned areasdatabase and storing LCI information from said list of LCIs in saidlocal database.
 15. The method of claim 14, wherein: area informationstored within said previously returned areas database is time limited.16. The method of claim 12, wherein: said response message comprises anempty list of LCIs at least partially in response to said firstdirectory server not finding any LCIs identifying areas in said vicinityof said estimated location.
 17. The method of claim 16, wherein: saidresponse message further comprises an indication of an area within whichsaid mobile device is not to transmit a subsequent request message ifsaid list of LCIs is empty.
 18. The method of claim 17, furthercomprising: after receiving said response message, storing saidindication of said area within which said mobile device is not totransmit a subsequent request message in a previously returned areasdatabase.
 19. An article comprising: a non-transitory storage mediumhaving machine-readable instructions stored thereon which are executableby a special purpose computing apparatus to: determine, at a mobiledevice, whether a location context identifier (LCI) is desired; search alocal database of said mobile device for LCI information using anestimated location of said mobile device at least partially in responseto determining that said estimated location is within areas previouslyreturned by one or more directory servers; and initiate transmission ofa request message for one or more LCIs from said mobile device at leastpartially in response to determining that said estimated location isoutside areas previously returned by said one or more directory servers,said request message comprising at least an indication of said estimatedlocation of said mobile device.
 20. A mobile device comprising: atransmitter; and a processor to: determine whether a location contextidentifier (LCI) is desired; search a local database of said mobiledevice for LCI information using an estimated location of said mobiledevice at least partially in response to determining that said estimatedlocation is within areas previously returned by one or more directoryservers; and initiate transmission of a request message through saidtransmitter for one or more LCIs from said mobile device at leastpartially in response to said estimated location being outside areaspreviously returned by said one or more directory servers, said requestmessage comprising at least an indication of said estimated location ofsaid mobile device.